-
Notifications
You must be signed in to change notification settings - Fork 139
Revert change to make preference nncp on worker nodes thatn master nodes #3367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert change to make preference nncp on worker nodes thatn master nodes #3367
Conversation
afa0f89 to
46add10
Compare
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-nodeset-values/values.yaml.j2
Show resolved
Hide resolved
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-nodeset-values/values.yaml.j2
Show resolved
Hide resolved
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-nodeset-values/values.yaml.j2
Show resolved
Hide resolved
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-values/values.yaml.j2
Show resolved
Hide resolved
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-values/values.yaml.j2
Show resolved
Hide resolved
It seems these scenarios has master nodes and a single worker node which is tainted. This worker node is used for running tempest but nothing related with OCP. Problematic scenarios are those which has a worker node tainted for tempest, but the workload is set in master nodes. There's no reason to configure NNCP in master nodes when we have regular worker nodes, so we were assuming that in case of there's a worker node, then all NNCP goes to worker node, which is problematic when single worker node is tainted. So we need to enhance the templates to: * Check if there's a worker node, if so, check if those are tainted. * If not tainted, worker takes preference. * If tainted, master takes preference. * If there's no worker node, then we go with master nodes. * Same for SNO CRC scenarios. Adding also uni02beta that takes the template from common
46add10 to
e990cff
Compare
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-nodeset-values/values.yaml.j2
Show resolved
Hide resolved
sdatko
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
roles/ci_gen_kustomize_values/templates/uni02beta/edpm-nodeset-values/values.yaml.j2
Show resolved
Hide resolved
arxcruz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: arxcruz, sdatko The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
It seems these scenarios has master nodes and a single worker node which is tainted. This worker node is used for running tempest but nothing related with OCP.
Problematic scenarios are those which has a worker node tainted for tempest, but the workload is set in master nodes.
There's no reason to configure NNCP in master nodes when we have regular worker nodes, so we were assuming that in case of there's a worker node, then all NNCP goes to worker node, which is problematic when single worker node is tainted.
So we need to enhance the templates to: